Skip to main content

VM Hardware Setups

What are the VM Hardware Setups?​

Hardware Setups are configuration templates used to define the hardware specifications for virtual machines.

What is the Difference Between Enabled vs. Disabled Debug in the VM Hardware Setups Table?​

Indicates whether or not the VM Hardware Setup has debugging enabled. When debug is enabled, system admins are fixing the VM hardware setup. There should never be any VM Hardware Setup in production with debug enabled, as that constitutes a high security risk.

What is the Difference Between Enabled vs. Disabled Advanced Options in the VM Hardware Setups Table?​

Indicates whether or not the system admin has enabled advanced options in the VM Hardware Setup. When this option is enabled, there are esoteric parameters in place which may create a different outcome for the VM Hardware Setup when released in production.

What is the Difference Between Enabled vs. Disabled VM Settings in the VM Hardware Setups Table?​

Indicates whether or not the VM settings have been altered for the VM Hardware Setup. This determines the type of VMs that can work with the specified VM Hardware Setup.

What is the Variant Column in the VM Hardware Setups Table?​

It displays the variant of the VM Hardware Setup, such as Beta for newly updated versions or versions that are under development, and Default for versions that are already stable and ready to run.

What is the Role of Start Up Script in VM Hardware Setups?​

Suppose you want to setup a form of login on a specific file or infrastructure in your VMs, or add a new custom VM group to the VM which is not generally available:

You can use the Start Up Script to run the login or group operations before the VM controller triggers the VM to start.

note

The Start Up Script is a shell terminal responding to custom pre-configured commands based on each VM hardware setup. The shell script is OS specific:

  • Runs bash scripts for Linux VMs.
  • Runs powershell for Windows VMs.

How does the Start Up Script in VM Hardware Setups Works in Practice?​

Whenever a VM starts, the VM downloads a VM controller locally. The VM runs the Startup Script and then starts the VM controller.

In this way, the commands in start up script shell terminal, run prior to the VM startup.

What is the Role of the XML Script in VM Hardware Setups?​

When a VM starts, it borrows information from the XML Script.

The XML script contains all the neccessary VM data, file sizes, drives, network interfaces, VM image, etc.

Once created, the XML is sent to the Libvirt daemon ( libvirtd).

What is the Purpose of the Configuration File Prefix in VM Hardware Setups?​

Whenever the VM controller starts, it reads the configuration file of the hardware setup. The configuration file contains vital information for the VM to start such as port, version to run on, wether or not to enable RDP or users with admin roles, etc. All VM configurations are located in the config file.

The small directory etc/ticrypt/controller.toml is the default configuration that is run by the VM controller.

If you type a different path in the file prefix field, the config file path changes.

What is the Purpose of the Image in VM Hardware Setups?​

Each VM hardware setup uses an image to function. Each image is check by the VM controller. The config file contains the image instructions for the hardware setup.

Can I Use the Same Image for Multiple VM Configurations in tiCrypt?​

Yes.​

tiCrypt allows you to use the same image for multiple VM Configurations.